Motivation and Context

Tools with complex object input schemas can be difficult to work with because we're only given a <textarea/> in the UI.

This change renders fields for nested object fields and also still gives the option to edit and format as JSON.

Example of nested fields:

Example of JSON mode:

How Has This Been Tested?

So far, this has been tested on my Windows machine using an extended version of the everything-server sampleLLM tool with complex inputs.

I could use some help testing with other real examples of complex inputs, where the current UI is too limited.

Breaking Changes

None

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

Related to this issue: #130